System for dynamic chaffing for log obfuscation based on shifting exposure portfolio

ABSTRACT

Systems, computer program products, and methods are described herein for dynamic chaffing for log obfuscation based on shifting exposure portfolio. The present invention is configured to receive an event log from one or more sources associated with a resource, wherein the event log comprises one or more event records generated based on one or more action incidences; initiate a chaffing engine on the event log; generate, using the chaffing engine, one or more artificial records based on at least the one or more event records; tag the one or more artificial records and the one or more event records with one or more authentication codes; interleave, using the chaffing engine, the one or more artificial records and the one or more event records to generate an encrypted event log with one or more chaffed event records; and store the encrypted event log in an event database.

FIELD OF THE INVENTION

The present invention embraces a system for dynamic chaffing for logobfuscation based on shifting exposure portfolio.

BACKGROUND

Understanding widespread security exposure allows entities to createsecurity issue awareness but may not often be the best focus forsecurity teams within the entities. Security and exposure managementleaders may be benefitted from approaching the exposure landscape basedon a continuous assessment of exposure and business evolutions andembrace a system for dynamic chaffing for log obfuscation based onshifting exposure portfolio.

SUMMARY

The following presents a simplified summary of one or more embodimentsof the present invention, in order to provide a basic understanding ofsuch embodiments. This summary is not an extensive overview of allcontemplated embodiments and is intended to neither identify key orcritical elements of all embodiments nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments of the present invention in a simplified form as aprelude to the more detailed description that is presented later.

In one aspect, a system for dynamic chaffing for log obfuscation basedon shifting exposure portfolio is presented. The system comprising: atleast one non-transitory storage device; and at least one processingdevice coupled to the at least one non-transitory storage device,wherein the at least one processing device is configured to: receive anevent log from one or more sources associated with a resource, whereinthe event log comprises one or more event records, wherein the one ormore event records are generated based on one or more action incidences;initiate a chaffing engine on the event log; generate, using thechaffing engine, one or more artificial records based on at least theone or more event records; tag the one or more artificial records andthe one or more event records with one or more authentication codes;interleave, using the chaffing engine, the one or more artificialrecords and the one or more event records to generate an encrypted eventlog with one or more chaffed event records; and store the encryptedevent log in an event database.

In some embodiments, the at least one processing device is furtherconfigured to tag the one or more event records, wherein tagging furthercomprises: generating, using the chaffing engine, one or more messageauthentication codes for the one or more event records; and tagging,using the chaffing engine, the one or more event records with the one ormore message authentication codes.

In some embodiments, the at least one processing device is furtherconfigured to tag the one or more artificial records, wherein taggingfurther comprises: generating, using the chaffing engine, one or morerandom authentication codes for the one or more artificial records; andtagging, using the chaffing engine, the one or more artificial recordswith the one or more random authentication codes.

In some embodiments, the at least one processing device is furtherconfigured to: receive an access request from a computing device of auser to access the event log; initiate an authentication protocol todetermine whether the user is authorized to access the event log; andinitiate a winnowing engine on the event log based on at leastdetermining that the user is authorized to access the event log.

In some embodiments, the at least one processing device is furtherconfigured to: initiate the authentication protocol, wherein initiatingfurther comprises: transmitting, via the computing device of the user,an authentication request; receiving, via the computing device of theuser, one or more authentication credentials from the user; validatingthe one or more authentication credentials; and determining that theuser is authorized to access the event log based on at least validatingthe one or more authentication credentials.

In some embodiments, the at least one processing device is furtherconfigured to validate the one or more authentication credentials,wherein validating further comprises: determining an authorization levelof the user based on at least the one or more authenticationcredentials; determining an authorization requirement associated withaccessing the event log; determining that the authorization level of theuser meets the authorization requirement associated with accessing theevent log; and determining that the user is authorized to access theevent log based on at least determining that the authorization level ofthe user meets the authorization requirement associated with accessingthe event log.

In some embodiments, the at least one processing device is furtherconfigured to: initiate the winnowing engine on the encrypted event logbased on at least determining that the user is authorized to access theevent log; retrieve, using the winnowing engine, the one or more chaffedevent records from the encrypted event log; identify, using thewinnowing engine, the one or more event records from the one or morechaffed event records based on at least the one or more authenticationcodes associated with the one or more chaffed event records; andtransmit control signals configured to cause the computing device of theuser to display the one or more event records identified.

In some embodiments, the at least one processing device is furtherconfigured to identify the one or more event records from the one ormore chaffed event records, wherein identifying further comprisesretrieving the one or more chaffed event records that are tagged withthe one or more message authentication codes.

In some embodiments, the at least one processing device is furtherconfigured to:

initiate a log correlation protocol on the one or more event records;cluster, using the log correlation protocol, the one or more eventrecords into one or more groups based on the one or more actionincidences; generate a representative event record for each of the oneor more groups based on at least one or more log correlation rules;update the event log with the one or more representative event recordsgenerated for the one or more groups.

In some embodiments, the at least one processing device is furtherconfigured to: determine an exposure portfolio associated with theresource; determine one or more obfuscation requirements associated withthe resource, wherein the one or more obfuscation requirements aredetermined based on the exposure portfolio; and initiate the chaffingengine on the event log associated with the resource based on at leastthe exposure portfolio, wherein the event log comprises the one or moreevent records.

In some embodiments, the at least one processing device is furtherconfigured to: determine a change in the exposure portfolio of theresource; determine a change in the one or more obfuscation requirementsbased on at least the change in the exposure portfolio of the resource;and initiate the chaffing engine on the event log associated with theresource based on at least the change in the exposure portfolio, whereinthe event log comprises the one or more representative event records.

In another aspect, a computer program product for dynamic chaffing forlog obfuscation based on shifting exposure portfolio is presented. Thecomputer program product comprising a non-transitory computer-readablemedium comprising code causing a first apparatus to: receive an eventlog from one or more sources associated with a resource, wherein theevent log comprises one or more event records, wherein the one or moreevent records are generated based on one or more action incidences;initiate a chaffing engine on the event log; generate, using thechaffing engine, one or more artificial records based on at least theone or more event records; tag the one or more artificial records andthe one or more event records with one or more authentication codes;interleave, using the chaffing engine, the one or more artificialrecords and the one or more event records to generate an encrypted eventlog with one or more chaffed event records; and store the encryptedevent log in an event database.

In yet another aspect, a method for dynamic chaffing for log obfuscationbased on shifting exposure portfolio is presented. The methodcomprising: receiving an event log from one or more sources associatedwith a resource, wherein the event log comprises one or more eventrecords, wherein the one or more event records are generated based onone or more action incidences; initiating a chaffing engine on the eventlog; generating, using the chaffing engine, one or more artificialrecords based on at least the one or more event records; tagging the oneor more artificial records and the one or more event records with one ormore authentication codes; interleaving, using the chaffing engine, theone or more artificial records and the one or more event records togenerate an encrypted event log with one or more chaffed event records;and storing the encrypted event log in an event database.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 illustrates technical components of a system for dynamic chaffingfor log obfuscation based on shifting exposure portfolio, in accordancewith an embodiment of the invention;

FIG. 2 illustrates a process flow for dynamic chaffing for logobfuscation based on shifting exposure portfolio, in accordance with anembodiment of the invention; and

FIG. 3 illustrates a process flow for dynamic winnowing for logobfuscation based on shifting exposure portfolio, in accordance with anembodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Where possible, any terms expressed in the singularform herein are meant to also include the plural form and vice versa,unless explicitly stated otherwise. Also, as used herein, the term “a”and/or “an” shall mean “one or more,” even though the phrase “one ormore” is also used herein. Furthermore, when it is said herein thatsomething is “based on” something else, it may be based on one or moreother things as well. In other words, unless expressly indicatedotherwise, as used herein “based on” means “based at least in part on”or “based at least partially on.” Like numbers refer to like elementsthroughout.

As used herein, an “entity” may be any institution employing informationtechnology resources and particularly technology infrastructureconfigured for processing large amounts of data. Typically, these datacan be related to the people who work for the organization, its productsor services, the customers or any other aspect of the operations of theorganization. As such, the entity may be any institution, group,association, financial institution, establishment, company, union,authority or the like, employing information technology resources forprocessing large amounts of data.

As described herein, a “user” may be an individual associated with anentity. As such, in some embodiments, the user may be an individualhaving past relationships, current relationships or potential futurerelationships with an entity. In some embodiments, a “user” may be anemployee (e.g., an associate, a project manager, an IT specialist, amanager, an administrator, an internal operations analyst, or the like)of the entity or enterprises affiliated with the entity, capable ofoperating the systems described herein. In some embodiments, a “user”may be any individual, entity or system who has a relationship with theentity, such as a customer or a prospective customer. In otherembodiments, a user may be a system performing one or more tasksdescribed herein.

As used herein, a “user interface” may be any device or software thatallows a user to input information, such as commands or data, into adevice, or that allows the device to output information to the user. Forexample, the user interface includes a graphical user interface (GUI) oran interface to input computer-executable instructions that direct aprocessing device to carry out specific functions. The user interfacetypically employs certain input and output devices to input datareceived from a user second user or output data to a user. These inputand output devices may include a display, mouse, keyboard, button,touchpad, touch screen, microphone, speaker, LED, light, joystick,switch, buzzer, bell, and/or other user input/output device forcommunicating with one or more users.

As used herein, an “engine” may refer to core elements of a computerprogram, or part of a computer program that serves as a foundation for alarger piece of software and drives the functionality of the software.An engine may be self-contained, but externally-controllable code thatencapsulates powerful logic designed to perform or execute a specifictype of function. In one aspect, an engine may be underlying source codethat establishes file hierarchy, input and output methods, and how aspecific part of a computer program interacts or communicates with othersoftware and/or hardware. The specific components of an engine may varybased on the needs of the specific computer program as part of thelarger piece of software. In some embodiments, an engine may beconfigured to retrieve resources created in other computer programs,which may then be ported into the engine for use during specificoperational aspects of the engine. An engine may be configurable to beimplemented within any general purpose computing system. In doing so,the engine may be configured to execute source code embedded therein tocontrol specific features of the general purpose computing system toexecute specific computing operations, thereby transforming the generalpurpose system into a specific purpose computing system.

As used herein, “authentication credentials” may be any information thatcan be used to identify of a user. For example, a system may prompt auser to enter authentication information such as a username, a password,a personal identification number (PIN), a passcode, biometricinformation (e.g., iris recognition, retina scans, fingerprints, fingerveins, palm veins, palm prints, digital bone anatomy/structure andpositioning (distal phalanges, intermediate phalanges, proximalphalanges, and the like), an answer to a security question, a uniqueintrinsic user activity, such as making a predefined motion with a userdevice. This authentication information may be used to authenticate theidentity of the user (e.g., determine that the authenticationinformation is associated with the account) and determine that the userhas authority to access an account or system. In some embodiments, thesystem may be owned or operated by an entity. In such embodiments, theentity may employ additional computer systems, such as authenticationservers, to validate and certify resources inputted by the plurality ofusers within the system. The system may further use its authenticationservers to certify the identity of users of the system, such that otherusers may verify the identity of the certified users. In someembodiments, the entity may certify the identity of the users.Furthermore, authentication information or permission may be assigned toor required from a user, application, computing node, computing cluster,or the like to access stored data within at least a portion of thesystem.

It should also be understood that “operatively coupled,” as used herein,means that the components may be formed integrally with each other, ormay be formed separately and coupled together. Furthermore, “operativelycoupled” means that the components may be formed directly to each other,or to each other with one or more components located between thecomponents that are operatively coupled together. Furthermore,“operatively coupled” may mean that the components are detachable fromeach other, or that they are permanently coupled together. Furthermore,operatively coupled components may mean that the components retain atleast some freedom of movement in one or more directions or may berotated about an axis (i.e., rotationally coupled, pivotally coupled).Furthermore, “operatively coupled” may mean that components may beelectronically connected and/or in fluid communication with one another.

As used herein, an “interaction” may refer to any communication betweenone or more users, one or more entities or institutions, and/or one ormore devices, nodes, clusters, or systems within the system environmentdescribed herein. For example, an interaction may refer to a transfer ofdata between devices, an accessing of stored data by one or more nodesof a computing cluster, a transmission of a requested task, or the like.

As used herein, a “resource” may refer to electronic componentsassociated with the technology infrastructure (e.g., system environmentdescribed herein) of the entity. These electronic components includesoftware components such as applications, databases, data files, and/orthe like, hardware components such as computing devices, networkdevices, and/or the like, network components such as server, client,peer, transmission medium, connecting devices, and/or the like, and anyother electronic component associated with the technologyinfrastructure.

FIG. 1 presents an exemplary block diagram of the system environment fordynamic chaffing for log obfuscation based on shifting exposureportfolio 100, in accordance with an embodiment of the invention. FIG. 1provides a unique system that includes specialized servers and systemcommunicably linked across a distributive network of nodes required toperform the functions of the process flows described herein inaccordance with embodiments of the present invention.

As illustrated, the system environment 100 includes a network 110, asystem 130, and a user input system 140. In some embodiments, the system130, and the user input system 140 may be used to implement theprocesses described herein, in accordance with an embodiment of thepresent invention. In this regard, the system 130 and/or the user inputsystem 140 may include one or more applications stored thereon that areconfigured to interact with one another to implement any one or moreportions of the various user interfaces and/or process flow describedherein.

In accordance with embodiments of the invention, the system 130 isintended to represent various forms of digital computers, such aslaptops, desktops, video recorders, audio/video player, radio,workstations, personal digital assistants, servers, wearable devices,Internet-of-things devices, augmented reality (AR) devices, virtualreality (VR) devices, extended reality (XR) devices automated tellermachine devices, electronic kiosk devices, blade servers, mainframes, orany combination of the aforementioned. In accordance with embodiments ofthe invention, the user input system 140 is intended to representvarious forms of mobile devices, such as personal digital assistants,cellular telephones, smartphones, and other similar computing devices.The components shown here, their connections and relationships, andtheir functions, are meant to be exemplary only, and are not meant tolimit implementations of the inventions described and/or claimed in thisdocument.

In accordance with some embodiments, the system 130 may include aprocessor 102, memory 104, a storage device 106, a high-speed interface108 connecting to memory 104, and a low-speed interface 112 connectingto low speed bus 114 and storage device 106. Each of the components 102,104, 106, 108, 111, and 112 are interconnected using various buses, andmay be mounted on a common motherboard or in other manners asappropriate. The processor 102 can process instructions for executionwithin the system 130, including instructions stored in the memory 104or on the storage device 106 to display graphical information for a GUIon an external input/output device, such as display 116 coupled to ahigh-speed interface 108. In other implementations, multiple processorsand/or multiple buses may be used, as appropriate, along with multiplememories and types of memory. Also, multiple systems, same or similar tosystem 130 may be connected, with each system providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system). In some embodiments, the system 130 may bea server managed by the business. The system 130 may be located at thefacility associated with the business or remotely from the facilityassociated with the business.

The memory 104 stores information within the system 130. In oneimplementation, the memory 104 is a volatile memory unit or units, suchas volatile random access memory (RAM) having a cache area for thetemporary storage of information. In another implementation, the memory104 is a non-volatile memory unit or units. The memory 104 may also beanother form of computer-readable medium, such as a magnetic or opticaldisk, which may be embedded and/or may be removable. The non-volatilememory may additionally or alternatively include an EEPROM, flashmemory, and/or the like. The memory 104 may store any one or more ofpieces of information and data used by the system in which it resides toimplement the functions of that system. In this regard, the system maydynamically utilize the volatile memory over the non-volatile memory bystoring multiple pieces of information in the volatile memory, therebyreducing the load on the system and increasing the processing speed.

The storage device 106 is capable of providing mass storage for thesystem 130. In one aspect, the storage device 106 may be or contain acomputer-readable medium, such as a floppy disk device, a hard diskdevice, an optical disk device, or a tape device, a flash memory orother similar solid state memory device, or an array of devices,including devices in a storage area network or other configurations. Acomputer program product can be tangibly embodied in an informationcarrier. The computer program product may also contain instructionsthat, when executed, perform one or more methods, such as thosedescribed above. The information carrier may be a non-transitorycomputer- or machine-readable storage medium, such as the memory 104,the storage device 104, or memory on processor 102.

In some embodiments, the system 130 may be configured to access, via thenetwork 110, a number of other computing devices (not shown) in additionto the user input system 140. In this regard, the system 130 may beconfigured to access one or more storage devices and/or one or morememory devices associated with each of the other computing devices. Inthis way, the system 130 may implement dynamic allocation andde-allocation of local memory resources among multiple computing devicesin a parallel or distributed system. Given a group of computing devicesand a collection of interconnected local memory devices, thefragmentation of memory resources is rendered irrelevant by configuringthe system 130 to dynamically allocate memory based on availability ofmemory either locally, or in any of the other computing devicesaccessible via the network. In effect, it appears as though the memoryis being allocated from a central pool of memory, even though the spaceis distributed throughout the system. This method of dynamicallyallocating memory provides increased flexibility when the data sizechanges during the lifetime of an application and allows memory reusefor better utilization of the memory resources when the data sizes arelarge.

The high-speed interface 108 manages bandwidth-intensive operations forthe system 130, while the low speed controller 112 manages lowerbandwidth-intensive operations. Such allocation of functions isexemplary only. In some embodiments, the high-speed interface 108 iscoupled to memory 104, display 116 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 111, which may acceptvarious expansion cards (not shown). In such an implementation,low-speed controller 112 is coupled to storage device 106 and low-speedexpansion port 114. The low-speed expansion port 114, which may includevarious communication ports (e.g., USB, Bluetooth, Ethernet, wirelessEthernet), may be coupled to one or more input/output devices, such as akeyboard, a pointing device, a scanner, or a networking device such as aswitch or router, e.g., through a network adapter.

The system 130 may be implemented in a number of different forms, asshown in FIG. 1. For example, it may be implemented as a standardserver, or multiple times in a group of such servers. Additionally, thesystem 130 may also be implemented as part of a rack server system or apersonal computer such as a laptop computer. Alternatively, componentsfrom system 130 may be combined with one or more other same or similarsystems and an entire system 130 may be made up of multiple computingdevices communicating with each other.

FIG. 1 also illustrates a user input system 140, in accordance with anembodiment of the invention. The user input system 140 includes aprocessor 152, memory 154, an input/output device such as a display 156,a communication interface 158, and a transceiver 160, among othercomponents. The user input system 140 may also be provided with astorage device, such as a microdrive or other device, to provideadditional storage. Each of the components 152, 154, 158, and 160, areinterconnected using various buses, and several of the components may bemounted on a common motherboard or in other manners as appropriate.

The processor 152 is configured to execute instructions within the userinput system 140, including instructions stored in the memory 154. Theprocessor may be implemented as a chipset of chips that include separateand multiple analog and digital processors. The processor may beconfigured to provide, for example, for coordination of the othercomponents of the user input system 140, such as control of userinterfaces, applications run by user input system 140, and wirelesscommunication by user input system 140.

The processor 152 may be configured to communicate with the user throughcontrol interface 164 and display interface 166 coupled to a display156. The display 156 may be, for example, a TFT LCD(Thin-Film-Transistor Liquid Crystal Display) or an OLED (Organic LightEmitting Diode) display, or other appropriate display technology. Thedisplay interface 156 may comprise appropriate circuitry and configuredfor driving the display 156 to present graphical and other informationto a user. The control interface 164 may receive commands from a userand convert them for submission to the processor 152. In addition, anexternal interface 168 may be provided in communication with processor152, so as to enable near area communication of user input system 140with other devices. External interface 168 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 154 stores information within the user input system 140. Thememory 154 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory may also be provided andconnected to user input system 140 through an expansion interface (notshown), which may include, for example, a SIMM (Single In Line MemoryModule) card interface. Such expansion memory may provide extra storagespace for user input system 140 or may also store applications or otherinformation therein. In some embodiments, expansion memory may includeinstructions to carry out or supplement the processes described aboveand may include secure information also. For example, expansion memorymay be provided as a security module for user input system 140 and maybe programmed with instructions that permit secure use of user inputsystem 140. In addition, secure applications may be provided via theSIMM cards, along with additional information, such as placingidentifying information on the SIMM card in a non-hackable manner. Insome embodiments, the user may use the applications to execute processesdescribed with respect to the process flows described herein.Specifically, the application executes the process flows describedherein.

The memory 154 may include, for example, flash memory and/or NVRAMmemory. In one aspect, a computer program product is tangibly embodiedin an information carrier. The computer program product containsinstructions that, when executed, perform one or more methods, such asthose described herein. The information carrier is a computer-ormachine-readable medium, such as the memory 154, expansion memory,memory on processor 152, or a propagated signal that may be received,for example, over transceiver 160 or external interface 168.

In some embodiments, the user may use the user input system 140 totransmit and/or receive information or commands to and from the system130 via the network 110. Any communication between the system 130 andthe user input system 140 (or any other computing devices) may besubject to an authentication protocol allowing the system 130 tomaintain security by permitting only authenticated users (or processes)to access the protected resources of the system 130, which may includeservers, databases, applications, and/or any of the components describedherein. To this end, the system 130 may require the user (or process) toprovide authentication credentials to determine whether the user (orprocess) is eligible to access the protected resources. Once theauthentication credentials are validated and the user (or process) isauthenticated, the system 130 may provide the user (or process) withpermissioned access to the protected resources. Similarly, the userinput system 140 (or any other computing devices) may provide the system130 with permissioned to access the protected resources of the userinput system 130 (or any other computing devices), which may include aGPS device, an image capturing component (e.g., camera), a microphone, aspeaker, and/or any of the components described herein.

The user input system 140 may communicate with the system 130 (and oneor more other devices) wirelessly through communication interface 158,which may include digital signal processing circuitry where necessary.Communication interface 158 may provide for communications under variousmodes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging,CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Suchcommunication may occur, for example, through radio-frequencytransceiver 160. In addition, short-range communication may occur, suchas using a Bluetooth, Wi-Fi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 170 mayprovide additional navigation—and location-related wireless data to userinput system 140, which may be used as appropriate by applicationsrunning thereon, and in some embodiments, one or more applicationsoperating on the system 130.

The user input system 140 may also communicate audibly using audio codec162, which may receive spoken information from a user and convert it tousable digital information. Audio codec 162 may likewise generateaudible sound for a user, such as through a speaker, e.g., in a handsetof user input system 140. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, etc.) and may also include sound generated by one or moreapplications operating on the user input system 140, and in someembodiments, one or more applications operating on the system 130.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in atechnical environment that includes a back end component (e.g., as adata server), that includes a middleware component (e.g., an applicationserver), that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components.

As shown in FIG. 1, the components of the system 130 and the user inputsystem 140 are interconnected using the network 110. The network 110,which may be include one or more separate networks, be a form of digitalcommunication network such as a telecommunication network, a local areanetwork (“LAN”), a wide area network (“WAN”), a global area network(“GAN”), the Internet, or any combination of the foregoing. It will alsobe understood that the network 110 may be secure and/or unsecure and mayalso include wireless and/or wired and/or optical interconnectiontechnology.

In accordance with an embodiments of the invention, the components ofthe system environment 100, such as the system 130 and the user inputsystem 140 may have a client-server relationship, where the user inputsystem 130 makes a service request to the system 130, the system 130accepts the service request, processes the service request, and returnsthe requested information to the user input system 140, and vice versa.This relationship of client and server typically arises by virtue ofcomputer programs running on the respective computers and having aclient-server relationship to each other.

It will be understood that the embodiment of the system environment 100illustrated in FIG. 1 is exemplary and that other embodiments may vary.As another example, in some embodiments, the system environment mayinclude more, fewer, or different components. As another example, insome embodiments, some or all of the portions of the system environment100 may be combined into a single portion. Likewise, in someembodiments, some or all of the portions of the system 130 may beseparated into two or more distinct portions.

FIG. 2 illustrates a process flow for dynamic chaffing for logobfuscation based on shifting exposure portfolio 200, in accordance withan embodiment of the invention. As shown in block 202, the process flowincludes receiving an event log from one or more sources associated witha resource, wherein the event log comprises one or more event records.An event log may be a local file that chronicles each event recordassociated with an action incidence, or “happenings” that occur with theresource. Event records may be automatically generated for actionincidences. Examples of action incidences may include, but are notlimited to, accessing, deleting, adding a file or an application,modifying the resource's date, shutting down the resource, errorincidences, changing the resource configuration, and/or the like.

In some embodiments, each resource may be associated with one or moresources. A source may be any software and/or hardware componentassociated with the resource. When an action incidence occurs, eachsource connected to the resource may be affected in some way. In suchcases, each source may be capable of generating an event record for thesame action incidence. As an example, a resource may include a number ofapplications installed thereon, where each application may be a source.Each application may have client event records, event records from aload balancer, event records from a web server, database event records,event records from worker services that handle longer-running tasks,and/or the like. A resource with more advance capabilities will have amore expansive event record and multiple event logs. Event recordsgenerated by each source may have a unique format, amplifying thedifficulty of tracing the action incidence using the event records. Toaddress these issues, the system may be configured to initiate a logcorrelation protocol on the one or more event records.

In some embodiments, the log correlation protocol may be used to moveall the logs to a centralized location and determine, using patternmatching software, which parts of disparate event records across thevarious sources represent the same action incidence. In response, thelog correlation protocol may be configured to cluster the one or moreevent records into one or more groups based on the one or more actionincidences. Once clustered, the log correlation protocol may beconfigured to generate a representative event record for each of the oneor more groups based on at least one or more log correlation rules. Asan example, log correlation rules specifies which sequences of eventrecords should be indicative of a particular action incidence, specifictime windows during which event records are recorded that areidentifiable based on individual time stamps, specific types of eventrecords that in combination identify the specific type of actionincidence, and/or the like. A representative event log may be used toidentify the action incidence and reduce the amount of memory used whenstoring the event log. In response, the system may be configured toupdate the event log with the one or more representative event recordsgenerated for the one or more groups.

In some embodiments, the system may be configured to determine anexposure portfolio associated with the resource. In one aspect, theexposure portfolio may be based on an exposure landscape associated withthe resource. An exposure landscape may include a collection ofpotential exposures that may affect a particular resource within adomain or context. In one aspect, the exposure landscape may identifyvulnerabilities in the resource, exposure vectors involved, and observedtrends. An exposure landscape can be broad, including an entire range ofpotentials exposures, or targeted at each resource within a particularsector or domain. Exposure landscapes may often shift and vary based onthe particular time horizon involved, including current exposurelandscapes, emergent exposure landscape, and future exposure landscapes,that reflect exposure to deployments of new technology, oftencharacterized by a low maturity regarding technical vulnerabilities.

Based on the exposure landscape, the system may be configured togenerate the exposure portfolio for the resource. In one aspect, theexposure portfolio may include exposure vectors capable of manipulatingresource element issues (e.g., gaps, redundancies, and/or deficienciesin elements of the resource) that could result in exposure to theresource. Exposure vectors are security pressures to the resource and/orthe entity. These security pressures may include any type of pressure tothe resource, such as but not limited to data exfiltration (e.g.,extraction, loss, of intellectual property data, customer data,financial data, entity data, or any other type of data), resource damage(e.g., viruses, physical damage, or the like), operational exposure(e.g., resource downtime, process downtime, manufacturing downtime, orthe like), or any other like exposure to which a resource could beexposed. As such, the exposure vectors may illustrate the individualcomponents of the exposures.

In response, the system may be configured to determine one or moreobfuscation requirements associated with the resource, wherein the oneor more obfuscation requirements are determined based on the exposureportfolio. In some embodiments, the obfuscation requirements mayidentify specific aspects of the resources (e.g., event log) that needto be obfuscation and/or protected to mitigate any exposure vectors.These aspects may relate to users, processes, and/or technologies thatcan use and/or have access to the specific aspects of the resource.Based on the obfuscation requirements, the system may be configured todetermine resource obfuscation tools. In some embodiments, the resourceobfuscation tools may include the processes in place for allowing accessto the specific aspects of the resource and/or the technology used(in-house and/or third party technology) associated with the obfuscationof the specific aspects of the resource.

One such technology/process is the chaffing and winnowing encryptionmethod. Chaffing and winnowing are dual components of aprivacy-enhancement scheme that does not require encryption. Thetechnique consists of adding false packets to a file, and then removingthe false packets when the file is accessed by authorized recipients.The false packets obscure the contents of the file and render the fileunintelligible to anyone except authorized personnel. In someembodiments, the system may be configured to initiate the chaffingengine on the event log associated with the resource based on at leastthe exposure portfolio.

Next, as shown in block 204, the process flow includes initiating achaffing engine on the event log. In some embodiments, the system may beconfigured to initiate the chaffing engine on the event log with one ormore event records based on a current exposure portfolio of theresource. However, the exposure portfolio of the resource may changebased on their exposure landscape. In this regard, the system may beconfigured to continuously monitor the exposure landscape for eachresource. By monitoring the exposure landscape of a resource, any shiftin the exposure landscape may be captured and recorded. Based on thecaptured shift in the exposure landscape of the resource, the system maybe configured to update the exposure portfolio for the resourceaccordingly. Any change to the exposure portfolio may trigger a changein the obfuscation requirements for the resource. If the monitoringrequirements change, the implementation of obfuscation tools on thespecific aspects of the resource may need re-evaluation. In such cases,the system may be configured to initiate the chaffing engine on theevent log with the one or more representative event records based on thechanged exposure portfolio. Event logs with event records may haveincreased processing requirements to implement chaffing and winnowingcompared to event logs with representative event records. However,implementing chaffing and winnowing on event records before correlationmay result in a more secure obfuscation compared to implementingchaffing and winnowing on representative event records, i.e., eventrecords post correlation. Based on the exposure portfolio of theresource, the system may be configured to dynamically determine whetherthe chaffing engine is implemented on the event log with event recordsor on event log with representative event records.

Next, as shown in block 206, the process flow includes generating, usingthe chaffing engine, one or more artificial records based on at leastthe one or more event records. In some embodiments, the system may beconfigured to generate synthetic data (artificial records) based on realdata (event records) while ensuring that the important statisticalproperties of real data are reflected in the synthetic data.

Next, as shown in block 208, the process flow includes tagging the oneor more artificial records and the one or more event records with one ormore authentication codes. In this regard, the system may be configuredto generate, using the chaffing engine, one or more messageauthentication codes for the one or more event records. In response, thesystem may be configured to tag, using the chaffing engine, the one ormore event records with the one or more message authentication codes.Similarly, the system may be configured to generate, using the chaffingengine, one or more random authentication codes for the one or moreartificial records. In response, the system may be configured to tag,using the chaffing engine, the one or more artificial records with theone or more random authentication codes. By tagging the event recordswith message authentication codes and artificial records with randomauthentication codes allows for easier identification and filtration ofevent records from the artificial records before being presented toauthorized personnel.

Next, as shown in block 210, the process flow includes interleaving,using the chaffing engine, the one or more artificial records and theone or more event records to generate an encrypted event log with one ormore chaffed event records. By interleaving the artificial records withthe event records in a pseudo-random pattern, the system may beconfigured to generate chaffed event records that are cryptographicallysecure without using process heavy encryption techniques. As the eventrecords are mixed with the artificial records, any unauthorizedpersonnel will not know which of the chaffed event records are the realevent records and which of the chaffed event records are artificialrecords. The tags are protected and stored by the system in a digitalkey repository and are retrieved and used only when authorized personnelrequest access to the event log.

Next, as shown in block 212, the process flow includes storing theencrypted event log in an event database. In some embodiments, thesystem may be configured to receive an access request from a computingdevice of a user to access the event log. In response, the system may beconfigured to initiate an authentication protocol to determine whetherthe user is authorized to access the event log. In this regard, thesystem may be configured to transmit, via the computing device of theuser, an authentication request. In response, the system may beconfigured to receive, via the computing device of the user, one or moreauthentication credentials from the user. In response, the system may beconfigured to validate the one or more authentication credentials. Inthis regard, the system may be configured to determine an authorizationlevel of the user based on at least the one or more authenticationcredentials. In addition, the system may be configured to determine anauthorization requirement associated with accessing the event log. Inresponse, the system may be configured to determine that theauthorization level of the user meets the authorization requirementassociated with accessing the event log. In response, the system may beconfigured to determine that the user is authorized to access the eventlog based on at least determining that the authorization level of theuser meets the authorization requirement associated with accessing theevent log. In response, the system may be configured to initiate awinnowing engine on the event log based on at least determining that theuser is authorized to access the event log.

FIG. 3 illustrates a process flow for dynamic winnowing for logobfuscation based on shifting exposure portfolio 300, in accordance withan embodiment of the invention. As shown in block 302, the process flowincludes initiating the winnowing engine on the encrypted event logbased on at least determining that the user is authorized to access theevent log. Next, as shown in block 302, the process flow includesretrieving, using the winnowing engine, the one or more chaffed eventrecords from the encrypted event log. Next, as shown in block 304, theprocess flow includes identifying, using the winnowing engine, the oneor more event records from the one or more chaffed event records basedon at least the one or more authentication codes associated with the oneor more chaffed event records. In this regard, the system may beconfigured to retrieving the one or more chaffed event records that aretagged with the one or more message authentication codes. Next, as shownin block 306, the process flow includes transmitting control signalsconfigured to cause the computing device of the user to display the oneor more event records identified.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, or thelike), an entirely hardware embodiment, or an embodiment combiningbusiness method, software, and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product thatincludes a computer-readable storage medium having one or morecomputer-executable program code portions stored therein. As usedherein, a processor, which may include one or more processors, may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing one or more computer-executableprogram code portions embodied in a computer-readable medium, and/or byhaving one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g. amemory) that can direct, instruct, and/or cause a computer and/or otherprogrammable data processing apparatus to function in a particularmanner, such that the computer-executable program code portions storedin the computer-readable medium produce an article of manufactureincluding instruction mechanisms which implement the steps and/orfunctions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. Accordingly, the terms “a” and/or “an”shall mean “one or more,” even though the phrase “one or more” is alsoused herein. Like numbers refer to like elements throughout.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

What is claimed is:
 1. A system for dynamic chaffing for log obfuscationbased on shifting exposure portfolio, the system comprising: at leastone non-transitory storage device; and at least one processing devicecoupled to the at least one non-transitory storage device, wherein theat least one processing device is configured to: receive an event logfrom one or more sources associated with a resource, wherein the eventlog comprises one or more event records, wherein the one or more eventrecords are generated based on one or more action incidences; initiate achaffing engine on the event log; generate, using the chaffing engine,one or more artificial records based on at least the one or more eventrecords; tag the one or more artificial records and the one or moreevent records with one or more authentication codes; interleave, usingthe chaffing engine, the one or more artificial records and the one ormore event records to generate an encrypted event log with one or morechaffed event records; and store the encrypted event log in an eventdatabase.
 2. The system of claim 1, wherein the at least one processingdevice is further configured to tag the one or more event records,wherein tagging further comprises: generating, using the chaffingengine, one or more message authentication codes for the one or moreevent records; and tagging, using the chaffing engine, the one or moreevent records with the one or more message authentication codes.
 3. Thesystem of claim 2, wherein the at least one processing device is furtherconfigured to tag the one or more artificial records, wherein taggingfurther comprises: generating, using the chaffing engine, one or morerandom authentication codes for the one or more artificial records; andtagging, using the chaffing engine, the one or more artificial recordswith the one or more random authentication codes.
 4. The system of claim3, wherein the at least one processing device is further configured to:receive an access request from a computing device of a user to accessthe event log; initiate an authentication protocol to determine whetherthe user is authorized to access the event log; and initiate a winnowingengine on the event log based on at least determining that the user isauthorized to access the event log.
 5. The system of claim 4, whereinthe at least one processing device is further configured to: initiatethe authentication protocol, wherein initiating further comprises:transmitting, via the computing device of the user, an authenticationrequest; receiving, via the computing device of the user, one or moreauthentication credentials from the user; validating the one or moreauthentication credentials; and determining that the user is authorizedto access the event log based on at least validating the one or moreauthentication credentials.
 6. The system of claim 5, wherein the atleast one processing device is further configured to validate the one ormore authentication credentials, wherein validating further comprises:determining an authorization level of the user based on at least the oneor more authentication credentials; determining an authorizationrequirement associated with accessing the event log; determining thatthe authorization level of the user meets the authorization requirementassociated with accessing the event log; and determining that the useris authorized to access the event log based on at least determining thatthe authorization level of the user meets the authorization requirementassociated with accessing the event log.
 7. The system of claim 6,wherein the at least one processing device is further configured to:initiate the winnowing engine on the encrypted event log based on atleast determining that the user is authorized to access the event log;retrieve, using the winnowing engine, the one or more chaffed eventrecords from the encrypted event log; identify, using the winnowingengine, the one or more event records from the one or more chaffed eventrecords based on at least the one or more authentication codesassociated with the one or more chaffed event records; and transmitcontrol signals configured to cause the computing device of the user todisplay the one or more event records identified.
 8. The system of claim7, wherein the at least one processing device is further configured toidentify the one or more event records from the one or more chaffedevent records, wherein identifying further comprises retrieving the oneor more chaffed event records that are tagged with the one or moremessage authentication codes.
 9. The system of claim 8, wherein the atleast one processing device is further configured to: initiate a logcorrelation protocol on the one or more event records; cluster, usingthe log correlation protocol, the one or more event records into one ormore groups based on the one or more action incidences; generate arepresentative event record for each of the one or more groups based onat least one or more log correlation rules; update the event log withthe one or more representative event records generated for the one ormore groups.
 10. The system of claim 9, wherein the at least oneprocessing device is further configured to: determine an exposureportfolio associated with the resource; determine one or moreobfuscation requirements associated with the resource, wherein the oneor more obfuscation requirements are determined based on the exposureportfolio; and initiate the chaffing engine on the event log associatedwith the resource based on at least the exposure portfolio, wherein theevent log comprises the one or more event records.
 11. The system ofclaim 10, wherein the at least one processing device is furtherconfigured to: determine a change in the exposure portfolio of theresource; determine a change in the one or more obfuscation requirementsbased on at least the change in the exposure portfolio of the resource;and initiate the chaffing engine on the event log associated with theresource based on at least the change in the exposure portfolio, whereinthe event log comprises the one or more representative event records.12. A computer program product for dynamic chaffing for log obfuscationbased on shifting exposure portfolio, the computer program productcomprising a non-transitory computer-readable medium comprising codecausing a first apparatus to: receive an event log from one or moresources associated with a resource, wherein the event log comprises oneor more event records, wherein the one or more event records aregenerated based on one or more action incidences; initiate a chaffingengine on the event log; generate, using the chaffing engine, one ormore artificial records based on at least the one or more event records;tag the one or more artificial records and the one or more event recordswith one or more authentication codes; interleave, using the chaffingengine, the one or more artificial records and the one or more eventrecords to generate an encrypted event log with one or more chaffedevent records; and store the encrypted event log in an event database.13. The computer program product of claim 12, wherein the firstapparatus is further configured to tag the one or more event records,wherein tagging further comprises: generating, using the chaffingengine, one or more message authentication codes for the one or moreevent records; and tagging, using the chaffing engine, the one or moreevent records with the one or more message authentication codes.
 14. Thecomputer program product of claim 13, wherein the first apparatus isfurther configured to tag the one or more artificial records, whereintagging further comprises: generating, using the chaffing engine, one ormore random authentication codes for the one or more artificial records;and tagging, using the chaffing engine, the one or more artificialrecords with the one or more random authentication codes.
 15. Thecomputer program product of claim 14, wherein the first apparatus isfurther configured to: receive an access request from a computing deviceof a user to access the event log; initiate an authentication protocolto determine whether the user is authorized to access the event log; andinitiate a winnowing engine on the event log based on at leastdetermining that the user is authorized to access the event log.
 16. Thecomputer program product of claim 15, wherein the first apparatus isfurther configured to: initiate the authentication protocol, whereininitiating further comprises: transmitting, via the computing device ofthe user, an authentication request; receiving, via the computing deviceof the user, one or more authentication credentials from the user;validating the one or more authentication credentials; and determiningthat the user is authorized to access the event log based on at leastvalidating the one or more authentication credentials.
 17. The computerprogram product of claim 16, wherein the first apparatus is furtherconfigured to validate the one or more authentication credentials,wherein validating further comprises: determining an authorization levelof the user based on at least the one or more authenticationcredentials; determining an authorization requirement associated withaccessing the event log; determining that the authorization level of theuser meets the authorization requirement associated with accessing theevent log; and determining that the user is authorized to access theevent log based on at least determining that the authorization level ofthe user meets the authorization requirement associated with accessingthe event log.
 18. The computer program product of claim 17, wherein thefirst apparatus is further configured to: initiate the winnowing engineon the encrypted event log based on at least determining that the useris authorized to access the event log; retrieve, using the winnowingengine, the one or more chaffed event records from the encrypted eventlog; identify, using the winnowing engine, the one or more event recordsfrom the one or more chaffed event records based on at least the one ormore authentication codes associated with the one or more chaffed eventrecords; and transmit control signals configured to cause the computingdevice of the user to display the one or more event records identified.19. The computer program product of claim 18, wherein the firstapparatus is further configured to identify the one or more eventrecords from the one or more chaffed event records, wherein identifyingfurther comprises retrieving the one or more chaffed event records thatare tagged with the one or more message authentication codes.
 20. Amethod for dynamic chaffing for log obfuscation based on shiftingexposure portfolio, the method comprising: receiving an event log fromone or more sources associated with a resource, wherein the event logcomprises one or more event records, wherein the one or more eventrecords are generated based on one or more action incidences; initiatinga chaffing engine on the event log; generating, using the chaffingengine, one or more artificial records based on at least the one or moreevent records; tagging the one or more artificial records and the one ormore event records with one or more authentication codes; interleaving,using the chaffing engine, the one or more artificial records and theone or more event records to generate an encrypted event log with one ormore chaffed event records; and storing the encrypted event log in anevent database.